Emergency call redirection systems and methods

ABSTRACT

Systems and methods are provided for connecting a caller to an alternate telephone number, such as 911, when a call to a private response center does not result in immediate assistance. In one example, when the call to the private response center does not connect, the communications device used to make the call may prompt the user to indicate that the call relates to an emergency, and the communications device may call the emergency services telephone number. Failure to connect may result when the call does not connect to a receiving party, or upon failure to timely reach a customer service representative. In another example, the call to the private response center may connect, but the private response center may signal the communications device that the call will not be handled immediately. The communications device may then prompt the user to indicate whether an alternate telephone number should be called.

BACKGROUND

Nearly all locations within the United States and Canada are now served by “911” emergency telephone service, and many other countries have similar services. In the 911 system, calls to the telephone number 911 are specially routed to a public safety answering point (PSAP), where a specially-trained dispatcher can assess the nature of the emergency, offer assistance, dispatch emergency services or law enforcement personnel to the source of the call, or provide other services. Many PSAPs are interconnected to allow routing calls and other information between them. The 911 service facilitates rapid response by the appropriate authorities in cases of emergency.

Some private organizations offer telephone-based assistance services, for example navigation assistance, concierge services, health monitoring services, and the like. While these private assistance services are not intended to replace the 911 system, in some cases a client of a private telephone assistance service may call the familiar private assistance service in the event of an emergency, rather than 911.

BRIEF SUMMARY

According to one aspect, a communications device includes an input interface, a transceiver, a microprocessor, and a computer readable memory. The computer readable memory holds microprocessor instructions that, when executed by the microprocessor, cause the communications device to receive an input via the input interface, and in response to the input, place a first call to a first telephone number that is not an emergency services telephone number. The instructions further cause the communications device to recognize that the first call failed to complete, recognize a particular state of the communications device, the state indicating that a second telephone number is to be called, and after recognition of the particular state, place a second call to the second telephone number using the transceiver. The second telephone number may be an emergency services telephone number. In some embodiments, the instructions, when executed by the microprocessor, cause the communications device to recognize that the first call failed to complete when no connection was made to a receiving party. In some embodiments, the instructions, when executed by the microprocessor, cause the communications device to recognize that the first call failed to complete when no confirmatory message is received within a predetermined time after the first call is placed. In some embodiments, the instructions may cause the communications device to prompt a user of the communications device to indicate using the input interface that the second telephone number is to be called. The particular state of the communications device may be that an input is received from a user of the communications device indicating that the second telephone number is to be called. In some embodiments, the input indicating that the second telephone number is to be called may be received via a button on the communications device, via an audible cue from the user of the communications device, or via a sensor that detects a mechanical manipulation of the communications device. The particular state of the communications device may be that no input has been received from a user of the communications device within a predetermined time interval. The communications device may be a wireless telephone. The input interface may comprise one and only one button. In some embodiments, the instructions, when executed by the microprocessor, cause the communications device to alter the behavior of the input interface after recognition that the first call failed to complete.

According to another aspect, a method of operating a communications device includes receiving, via an input interface of the communications device, an input from a user of the communications device and in response to the input, under control of a processor comprised in the communications device, placing a first call to a first telephone number that is not an emergency services telephone number. The method further includes recognizing that the first call failed to complete, recognizing a particular state of the communications device, the state indicating that a second telephone number is to be called, and after recognition of the particular state, placing a second call to the second telephone number using the transceiver. The second telephone number may be an emergency services telephone number. In some embodiments, recognizing that the first call failed to complete includes recognizing that the first call did not result in a connection to a receiving party. In some embodiments, recognizing that the first call failed to complete includes recognizing that no confirmatory message is received within a predetermined time after the first call is placed. In some embodiments, the method further includes prompting a user of the communications device to indicate using the input interface that the second telephone number is to be called. Recognizing the particular state of the communications device may include recognizing that an input is received from a user of the communications device indicating that the second telephone number is to be called. In some embodiments, the input indicating that the second telephone number is to be called may be received via a button on the communications device, via an audible cue from the user of the communications device, or via a sensor that detects a mechanical manipulation of the communications device. In some embodiments, recognizing the particular state of the communications device includes recognizing that no input has been received from a user of the communications device within a predetermined time interval.

According to another aspect, a communications device includes an input interface, a transceiver, a microprocessor, and a computer readable memory. The computer readable memory holds microprocessor instructions that, when executed by the microprocessor, cause the communications device to receive an input via the input interface, and in response to the input, place a first call to a first telephone number that is not an emergency services telephone number. The instructions further cause the communications device to recognize a predetermined signal from the recipient of the first call, the predetermined signal indicating that the call has been rejected, recognize a particular state of the communications device, the particular state indicating that a second telephone number is to be called, and upon recognition of the particular state, place a second call to the second telephone number using the transceiver. The second telephone number may be an emergency services telephone number. The predetermined signal may be communicated from the recipient of the first call to the communications device via a dual tone multiple frequency (DTMF) signal or via a short message service (SMS) message. In some embodiments, the instructions, when executed by the microprocessor, cause the communications device to prompt a user of the communications device to indicate using the input interface that the second telephone number is to be called. The particular state of the communications device may be that an input is received from a user of the communications device indicating that the second telephone number is to be called. The particular state of the communications device may be that no input has been received from a user of the communications device within a predetermined time interval. The communications device may be a wireless telephone. In some embodiments, the instructions, when executed by the microprocessor, cause the communications device to alter the behavior of the input interface after recognition of the predetermined signal.

According to another aspect, a method of operating a communications device includes receiving, via an input interface of the communications device, an input from a user of the communications device, and in response to the input, under control of a processor comprised in the communications device, placing a first call to a telephone number that is not an emergency services telephone number. The method further concludes recognizing a predetermined signal from the recipient of the first call, the predetermined signal indicating that the call has been rejected, recognizing a particular state of the communications device, the particular state indicating that a second telephone number is to be called, and upon recognition of the particular state, placing a second call to the second telephone number using the transceiver. The second telephone number may be an emergency services telephone number. Recognizing the predetermined signal may include recognizing a predetermined signal that is communicated from the recipient of the first call to the communications device via a dual-tone multiple-frequency (DTMF) signal or recognizing a predetermined signal that is communicated from the recipient of the first call to the communications device via a short message service (SMS) message. In some embodiments, the method further includes prompting a user of the communications device to indicate using the input interface that the second telephone number is to be called. Recognizing the particular state of the communications device may include recognizing that an input is received from a user of the communications device indicating that the second telephone number is to be called. Recognizing the particular state of the communications device may include recognizing that no input has been received from a user of the communications device within a predetermined time interval.

In another aspect, a method for operating a service center includes receiving a call at the service center from a communications device, determining that the call will not be answered by a customer service representative within a predetermined time, and sending a signal to the communications device indicating that the call is rejected. Sending a signal to the communications device indicating that the call is rejected may include sending a dual tone multiple frequency (DTMF) signal across an audio link between the service center and the communications device. Sending a signal to the communications device indicating that the call is rejected may include sending a short message service (SMS) message from the service center to the communications device.

According to another aspect, a method for operating a service center includes receiving a call at the service center from a communications device, connecting the call with a customer service representative, and upon connecting the call with the customer service representative, sending a confirmatory message to the communications device indicating that the call has been answered by the customer service representative. Sending the confirmatory message to the communications device indicating that the call has been answered by the customer service representative may include sending a short message service (SMS) message.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified schematic diagram of a cellular telephone network.

FIG. 2 is a simplified block diagram of network controller illustrating interfaces in accordance with an embodiment.

FIG. 3 illustrates an exemplary communications device.

FIG. 4 illustrates entities involved in a typical scenario in accordance with an embodiment.

FIG. 5 illustrates a sequence of operations that may be performed by a communications device, in accordance with embodiments.

FIG. 6 illustrates an interaction of a private response center and a communications device, in accordance with embodiments.

FIG. 7 illustrates another kind of interaction of a private response center and a communications device, in accordance with embodiments.

FIG. 8 illustrates a simplified block diagram of an exemplary communications device suitable for use in embodiments.

DETAILED DESCRIPTION

The ensuing description provides preferred exemplary embodiment(s) only, and is not intended to limit the scope, applicability or configuration of the disclosure. Rather, the ensuing description of the preferred exemplary embodiment(s) will provide those skilled in the art with an enabling description for implementing a preferred exemplary embodiment. It is understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope as set forth in the appended claims.

Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, systems, structures, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known processes, procedures and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process may be terminated when its operations are completed, but could have additional steps not included in a figure. Furthermore, embodiments may be implemented by manual techniques, automatic techniques, or any combination thereof.

FIG. 1 is a simplified schematic diagram of a cellular telephone network 100. Cellular networks are an especially efficient way to provide mobile telephone service. Each cell 101 is served by a base station 102, which often includes an antenna mounted on a tower 103. Each cellular telephone active in a particular cell can bi-directionally interact with the base station of the cell, enabling full duplex communication of data and/or voice. Each cell 101 is capable of communicating with mobile telephones 105 within the respective cell 101 according to a physical interface scheme (e.g., CDMA, LTE, GSM, GPRS, WiMax, etc.). Each base station 102 typically is capable of communicating simultaneously with several dozen different mobile telephones 105.

Adjacent cells 101 use different frequencies or coding to avoid interference. In this way, many mobile telephones can be supported using a limited spectra. The size and density of the cells 101 may be determined in part by the demand for service. While only three cells 101 are shown in FIG. 1, many cells 101 may be present. Special hand-off protocols may be used for maintaining communication with a particular telephone that moves from one cell 101 to another during a call.

As shown in FIG. 1, each base station 102 communicates with a network controller 104. It will be understood that FIG. 1 is highly simplified, and network controller 104 represents a wide array of hardware, software, and other components performing a wide variety of functions. For example, network controller 104 may route calls between cells 101 and outside telephone providers, monitor telephone usage, maintain billing records for individual telephone accounts, perform diagnostic tests, and perform many other functions.

Network controller 104 may also include interfaces between network 100 and other networks, organizations, or services. For example, FIG. 2 is a block diagram of network controller 104, still highly simplified, illustrating interfaces 205, 206, 207, 208 to the Internet 201, a plain old telephone system (POTS) 202, a PSAP 203, and a private response center (PRC) 204. Other interfaces to location services, data services, billing systems, toll-free number routing services, etc. are typical, but not shown.

WAN interface 205 connects network 100 with the Internet 201. The Internet 201 is a global system of interconnected computer networks, and enables digital communication between computers. Applications of the Internet 201 include the carrying of electronic mail, audio and video feeds, and other kinds of digital messages. One especially popular use of the Internet 201 is for the hosting and viewing of interlinked documents on the World Wide Web. Many modern mobile telephones, including cellular telephones of the kind supported by network 100, include the capability to access documents and communications through the Internet 201, for example sending and receiving electronic mail and viewing web pages. Other embodiments could us a wide area network (WAN) separate from or tunneled through the Internet 201.

POTS interface 206 connects network 100 with the plain old telephone system (POTS) 202. POTS 202 comprises, for example, a large number of traditional wireline telephones and other communications equipment, as well as the infrastructure required to support them. Many residential and small business telephones are part of POTS 202, which may still support telephone hardware that is decades old. POTS interface 206 enables users of mobile telephones that are part of network 100 to call telephones that utilize POTS 202, and vice versa.

Emergency interface 207 connects network 100 to PSAP 203, so that calls to the 911 emergency number made by mobile phone users on network 100 can be routed to a PSAP 203 or routed between multiple PSAPs 203. The PSAP 203 may be additionally served by POTS 202, or by another system.

Private response interface 208 connects network 100 to private response center 204. For example, private response center 204 may be operated by a service provider who offers personalized assistance to clients who subscribe to the service. In some embodiments, the service provider may offer personal health management advice, concierge services, navigational assistance, technical support for telephones used in conjunction with the service, or other kinds of personalized services deliverable by telephone. Private response center 204 may be staffed by customer service representatives who answer inquiries from clients of the service. Such a service may especially appeal to clients with health or other impairments. For example, the service could include weekly or daily calls to the client for verification that the client is doing well, and if not, the customer service representative may offer to contact a family member, health care provider, or other resource that may be helpful to the client. The service could include these and other services sold as a package.

Private response center (PRC) 204 is not intended to be a substitute for the PSAP 203. A client of the service offered by private response center 204 would still be expected to dial 911 in the event of an emergency.

In one example scenario, the service provider that operates private response center 204 may also be a cellular telephone service provider, and may offer a private assistance service as an adjunct to cellular telephone service. The private response center 204 can be contacted for non-emergency service through a phone number, speed dial or other shortcut, for example by activating a 5 and * key combination. The connection between network controller 104 and private response center 204 is schematic. The actual connection could be by way of the Internet 201, a wireless connection, a voice-over-Internet-protocol (VOIP) connection, a cellular telephone connection, or private response center 204 could be reached through POTS 202, or any other suitable connection method that enables a telephone user to reach private response center 204 by calling a telephone number. Private response center 204 may be reachable via multiple methods.

FIG. 3 illustrates a specialized communications device 301 that may be especially useful for some clients of private response center 204. Exemplary communications device 301 may internally be a fully-featured cellular telephone, but has a simplified input interface comprising only one button 302. Communications device 301 may also be referred to as a “fob” or an “emergency communicator.” A client of private response center 204 may wear communications device 301 on his or her person, and can use it to contact private response center 204 whenever assistance is needed. For example, communications device 301 may be configured to dial private response center 204 when button 302 is pressed. This greatly simplified input interface may be especially helpful to clients with impairments such as poor vision or coordination that make it difficult to operate a conventional cellular telephone that has many small keys. The single-button interface assures that private response center 204 will be called without the client having to press a sequence of keys. In the event of an emergency, the client may be distraught or disoriented, and the simplified input interface increases the chance of the client reaching private response center 204.

While embodiments are described using simplified communications device 301, other kinds of communications devices could also be used. For example, embodiments could utilize a conventional cellular telephone or smart phone having a full telephone keypad or even an alphanumeric keyboard. Other embodiments could utilize a pager, personal digital assistant, portable computer, or any other kind of communications device usable within the scope of the appended claims.

Communications device 301 further includes a microphone 303 and a speaker 304, enabling telephone or telephone-like communication. In some embodiments, communications device does not even include a display, although one may be included on which messages can be shown to the user. In some embodiments, communications device 301 may include an accelerometer 305. Accelerometer 305 may be used, for example, to detect that the user of communications device 301 has fallen, so that private response center 204 can be automatically contacted in that event. Accelerometer 305 may also be used to provide input to communications device 301, and may thus be considered part of the input interface of communications device 301. Microphone 303 may also be considered part of the input interface. That is, the input interface of example communications device 301 comprises one and only one button 302, and also comprises microphone 303 and accelerometer 305. Many other input interface configurations are possible, including configurations having more or fewer input devices. More details about the internal architecture of communications device 301 are given below.

FIG. 4 illustrates the entities involved in a typical scenario in accordance with an embodiment. As shown in FIG. 4, private response center 204 preferably comprises a computer system 401 that facilitates many of the functions of private response center 204. Computer system 401 includes a display screen 402 and an input device 403 for displaying information to and receiving inputs from a service representative 404. Input device 403 may be, for example, a keyboard, mouse, or other kind of input device or a combination of input devices. While computer system 401 is depicted in FIG. 3 as a single, stand-alone computer, computer system 401 may include multiple interconnected computers, which may be collocated or widely distributed. Computer system 401 may include various forms of data storage, including volatile and nonvolatile memory, and long term data storage. At least some of the data storage holds instructions executable by a processor of computer system 401 to perform functions in accordance with embodiments. In the example of FIG. 4, private response center 204 is connected to network controller 104 through multiple channels, including the Internet 201, and a telephone connection 405, which may be a wireline connection, wireless connection, or any other connection that enables private response center 204 to make and receive telephone calls. Many other arrangements are possible. For example, private response center 204 may be able to make and receive telephone calls over the Internet 201 using a voice-over-IP system.

As is explained above, a client of private response center 204 may use communications device 301 in a variety of scenarios. For example, the client may simply be driving and may wish to obtain driving directions, or the name of a nearby restaurant. However, the client may also use communications device 301 in the event of an emergency, such as an auto accident, a fall in the home, a sudden medical emergency, or other situation. The client may simply be familiar with the use of communications device 301 and may prefer to use it rather than calling 911 directly, or the client may not be near another telephone and may use communications device 301 of necessity. If the client's call from communications device 301 to private response center 204 is answered quickly, then customer service representative 404 may recognize that the client has an emergency, and may redirect the client's call to PSAP 203. Or customer service representative 404 may set up a conference call that includes the client, customer service representative 404, and PSAP 203 so that customer service representative 404 can advocate on behalf of the client. For example, customer service representative 404 may be able to access information about the client, such as a list of medications the client is taking, and provide the information to the emergency services personnel at PSAP 203.

Problems may arise, however, if the call to private response center 204 does not complete. For example, a partial telephone network outage or other problem may exist, so that the call to private response center 204 fails to connect to private response center 204, the intended receiving party. In another example of failure to complete, the call may be answered by private response center 204, but due to high call volume or other circumstances may be placed on hold and not taken up immediately by customer service representative 404. If the call relates to an emergency, it is highly desirable that some mechanism be provided for the client to be redirected to PSAP 203 as soon as possible.

In one embodiment, communications device 301 recognizes that the call failed to complete. However, due to the simple input interface of communications device 301, communications device 301 has no way to “know” whether the call relates to an emergency, or relates to some non-emergency request for assistance. Accordingly, communications device 301 may be configured to carry out a sequence of steps designed to connect the client to PSAP 203 as quickly as possible in an emergency, but to preferably avoid calls to 911 when no emergency is present.

FIG. 5 illustrates one sequence of operations that may be performed by communications device 301, in accordance with embodiments.

In step 501, communications device 301 receives an input from its input interface. For example, communications device 301 may recognize that button 302 has been pressed. Communications device 301 then places a call to private response center 204 at step 502. If the call goes through as normal, as determined in step 503, communications device 301 connects to private response center 204 at step 504. Customer service representative 404 may then render assistance to the client. When the purpose of the call has been served, the call can be ended at step 505, and communications device 301 goes idle. In some embodiments, the client may terminate the call by pressing button 302 a second time, or some other mechanism may be used to end the call. For example, communications device 301 may recognize that private response center 204 has disconnected, and may enter the idle state automatically.

If the check at step 503 determines that the call to private response center 204 did not complete, then communications device 301 may prompt the client to indicate whether the call relates to an emergency or not. For example, communications device 301 may recognize that the call to private response center 204 did not complete, and may play an audible message through speaker 304, indicating communications device 301 will call 911 if button 302 is pressed again within a predetermined time interval. As is shown in FIG. 5, the interval may be five seconds, but any other suitable interval may be used.

At step 507, communications device 301 determines whether button 302 was pressed or not. If not, communications device enters its idle state. However, if button 302 was pressed, that is, the client indicated that 911 should be called, communications device 301 calls 911 at step 508. The network outage or other problem that caused the original call to fail may not hinder the 911 call. In this way, communications device may connect the client to 911 in an emergency during which private response center 204 cannot be reached, but unnecessary calls to 911 are avoided. In this example, the default behavior of communications device 301 is to not call 911 when private response center 204 cannot be reached.

Many variations on this example sequence are possible. For example, the prompt delivered at step 506 and the test performed at step 507 could be configured such that 911 is called if the client does not press button 302 during the predetermined time interval, rather than if the client does press button 302. In that configuration the default behavior of communications device 301 would be to call 911 when private response center 204 cannot be reached.

The test depicted at step 507 is one example of communications device 301 recognizing that it is in a particular state. In the example of FIG. 5, the particular state that causes 911 to be called is that an input is received from a user of communications device 301 indicating that 911 is to be called. That is, the user pressed button 302 within the predetermined time interval. In another embodiment, as described above, the particular state that causes 911 to be called may be that no input was received from the user during the predetermined time interval.

Many other variations are possible. For example, the client could be prompted to shake communications device 301 to indicate that 911 should be called, or some other mechanical manipulation of communications device 301 could be sensed. Or the client could provide an audible cue to communications device 301 that 911 is to be called, for example by speaking into microphone 303 during a predetermined time interval. In some embodiments, communications device 301 may include voice recognition software that enables communications device 301 to recognize the audible cue from the client. When voice recognition software is present, more extensive interaction may be possible between the client and communications device 301 than simply indicating whether 911 is to be called, and communications device 301 may be directed to take any of several actions. For example, the client may say “call 911” to instruct communications device to call 911. In another example, the client may say “call another number” to direct communications device 301 to call an alternate number. The client may then may speak the number that communications device 301 is to call, and may be prompted to do so by communications device 301. In another example, the client may say “do nothing” or “hang up” to indicate that no action is to be taken. Communications device 301 may audibly interact with the client, for example prompting the client to indicate what action is to be taken, listing possible actions to be taken and the voice commands that initiate them, repeating inputs from the client to verify accuracy, and the like.

In the example of FIG. 5, communications device 301 may alter the behavior of its input interface when it recognizes that the call to private response center 204 did not complete. In ordinary use, single button 302 may be used both to initiate a call to private response center 204 and to terminate the call. However, once it is recognized that an attempted call to private response center 204 did not go through, the behavior of button 302 may be changed, so that pressing button 302 within the predetermined time interval causes communications device 301 to call 911, rather than terminating a call or placing communications device 301 in an idle state.

In some cases, a call to private response center 204 may fail to complete even if the telephone network is functioning properly. For example, a call from communications device 301 may connect to private response center 204, but private response center 204 may be experiencing heavy call volume, and may place the call on “hold” or into a queue for answering. An automated voice response system, which may be part of computer system 401, may inform the client of the expected wait time or provide other information until customer service representative 404 can pick up the call in person. If the client calling private response center 204 has an emergency, this answering delay may be detrimental. In this scenario, the call from communications device 301 to private response center 204 connects normally, and communications device 301 by itself may have no way to detect whether the connected call was answered by customer service representative 404 or by an automated system. Even if the voice response system indicates to the client that the call will not be handled promptly and that the client should call 911 if the call relates to an emergency, problems may still arise. For example, communications device 301 may have a simplified interface as shown in FIG. 3, wherein the single button 302 is configured to call private response center 204. Even though communications device 301 may be capable of calling numbers other than that of private response center 204, the user may have no way to initiate such a call. To call 911 (or another preselected alternate number) the client would then have to locate another working telephone. If the client is incapacitated, this may not be possible.

In some embodiments, communications device 301 can still detect that the call did not complete (did not reach a customer service representative), either on its own or based on the behavior of private response center 204. For example, communications device 301 may include voice recognition software that recognizes the content of a recorded voice message supplied by a voice response system. Communications device 301 may determine from the voice message that the call will not be handled within a predetermined expected answering time, for example two minutes, and may conclude that the call has therefore not completed. The predetermined expected answering time be any suitable interval, for example 30 seconds, one minute, two minutes, five minutes, or another time interval.

In some embodiments, automated systems at private response center 204 interact with communications device 301 so that the user may be redirected to 911 in the case of an emergency, when private response center 204 cannot handle the user's call immediately.

FIG. 6 illustrates one kind of interaction of private response center 204 and communications device 301 in accordance with embodiments.

In step 601, communications device 301 receives an input indicating that a call is to be placed to private response center 204. For example, a user of communications device 301 may push button 302, or a user of a different kind of communications device may dial a telephone number or press a sequence of keys. At step 602, communications device 301 calls private response center 204.

At step 603, private response center 204 receives the call. At step 604, private response center 204 checks to see if the call will be handled promptly by customer service representative 404. If so, the call is handled normally, either immediately by customer service representative 404, or the call is placed on hold for a short time, as shown in step 605.

If the call cannot be handled immediately or within a predetermined time, private response center 204 sends a signal to communications device 301 rejecting the call, as shown in step 606. For the purposes of this disclosure, to “reject” a call simply means to send a signal indicating that some circumstance interferes with the prompt handling of the call by private response center 204. Private response center 204 preferably does not disconnect the call. As indicated at step 607, communications device receives the rejection signal. (If no signal is received, the call proceeds as normal.)

The signal indicating that the call is rejected may take any suitable form. For example, equipment associated with private response center 204 may cause a series of dual-tone multiple-frequency (DTMF) tones to be transmitted on the line. In other embodiments, another kind of audio signal could be transmitted over the open phone line as the signal. Communications device 301 may be configured to recognize the DTMF tones or other audio signal as the signal indicating that the call is rejected. In other embodiments, private response center 204 may send a short message service (SMS) or “text” message to communications device indicating that the call is rejected. In any case, private response center 204 communicates to communications device 301 that the call will not be answered promptly by customer service representative 404.

Communications device 301 may then prompt the client to indicate whether 911 should be called, as illustrated in step 608. For example, communications device 301 may play an audible prompt through speaker 304, prompting the user to press button 302 again if the call relates to an emergency. In step 609, communications device recognizes whether button 302 has been pressed or not. If not, the call may be ended, or may continue to hold, as shown in step 610. If button 302 is pressed, communications device terminates the call to private response center 204 and calls 911, as shown in step 611.

Other variations are possible. In the example described above, communications device 301 recognizes that it is in a particular state that indicates that 911 is to be called—namely that the call has been rejected and the user has indicated by pressing button 302 that 911 is to be called. Other particular states could be used. For example, the user could be prompted that 911 will be called unless button 302 is pressed within a certain time interval. In that case, the particular state that indicates 911 is to be called is that no input has been received from a user of the communications device 301 within the predetermined time interval. In other embodiments, communications device 301 may automatically call 911 when a call is rejected, in which case the state that indicates 911 is to be called is simply that the call to private response center 204 was rejected. In another possible variation, the user prompt could be supplied by private response center 204 over the phone line, rather than being generated locally by communications device 301.

In some embodiments, communications device 301 may alter the behavior of its input interface after recognition of the signal indicating the call has been rejected by private response center 204. For example, in normal operation when a call to private response center is handled promptly by customer service representative, a subsequent press of button 302 may terminate the call. However, once communications device 301 recognizes that the call is rejected, it may change its behavior such that a subsequent press of button 302 results in a call to 911.

FIG. 7 illustrates another kind of interaction of private response center 204 and communications device 301 in accordance with embodiments. In this scenario, private response center 204 may have a policy of sending a confirmatory message to the initiating device when a call is taken up by customer service representative 404. For example, when a call is received from communications device 301, the call may be answered immediately by customer service representative 404, and a confirmatory SMS message sent to communications device 301 confirming that the call has been answered. Or, the call may be initially placed on hold or in an answering queue, and answered later by customer service representative 404. In that case, the confirmatory message is delayed until the call is answered by customer service representative 404.

As illustrated in FIG. 7, in step 701, communications device 301 receives an input indicating that a call is to be placed to private response center 204. For example, a user of communications device 301 may push button 302, or a user of a different kind of communications device may dial a telephone number or press a sequence of keys. At step 702, communications device 301 calls private response center 204. At step 703, private response center 204 receives the call, and may optionally place the call on hold in step 704. In parallel, once the call is placed, communications device 301 begins at step 705 monitoring incoming messages for a corresponding confirmatory message indicating that the call has been answered by customer service representative 404. If customer service representative 404 answers the call immediately or quickly at step 706, and sends the confirmatory message at step 707, then communications device 301 recognizes at step 708 that the confirmatory message has been timely received (within a predetermined maximum hold time after placing the call), and customer service representative handles the call as normal at step 709. In some cases, the caller and customer service representative 404 may already be conversing during the sending and receipt of the confirmatory message. Any suitable maximum hold time interval may be used, for example 30 seconds, 1 minute, 2 minutes, 5 minutes, or another time interval.

However, if no confirmatory message arrives at communications device 301 within the predetermined interval, communications device 301 may conclude that the call has not completed and prompts the user at step 710 whether an alternate number such as 911 should be called. If the user indicates that the alternate number is to be called, for example by pressing the button, communications device 301 recognizes that fact at step 711. Communications device then 301 terminates the call to private response center 204 and calls the alternate number at step 712. If the caller does not indicate that the alternate number is to be called, then the call continues to hold at step 713, and is answered in turn by customer service representative 404.

Other variations are possible, as described above. For example, communications device 301 may terminate the call to private response center 204 and call the alternate number if the caller does not press the button. And while embodiments have been described primarily as redirecting a call to an emergency services telephone number such as 911, it will be recognized that other alternate numbers may be used. For example, communications device 301 may be programmed to call a family member of the user if it is not possible immediately reach customer service representative 404 at private response center 204.

Embodiments exemplified by FIG. 7 may have the advantage that any kind of failure to complete a call is handled automatically. When no confirmatory message is received, communications device 301 can act accordingly to redirect the call to 911 or another alternate number, whether the failure to receive a confirmatory message was due to a network outage that prevented private response center 204 from receiving the call, or whether the failure to receive a confirmatory message was due to the inability of private response center 204 to connect the call with a customer service representative immediately. In these embodiments, the correct result is achieved in either case, and does not depend on the positive rejection of a call by private response center 204.

FIG. 8 illustrates a simplified block diagram of a communications device 801, suitable for use in embodiments. Communications device 800 may be a simplified communicator such as communications device 301, or may be another kind of communications device. Communications device 800 includes a radio transceiver 801 for communicating with network 100, an input interface 802 for receiving inputs from the user of communications device 800. Input interface 802 may include a single button or a multi-key keypad, and may include a microphone, an accelerometer, or other input devices. A display 803 may optionally be included for communicating information to the user. Display 803, if included, may comprise any means of visually communicating information to the user. For example, display 803 may comprise a backlit or passive liquid crystal display (LCD) or another kind of display capable of showing graphical or alphanumeric information. Display 803 could comprise a simple set of indicator lights, for example made of light emitting diodes or another kind of light source. Many other kinds of displays are possible. The operation of communications device 800 is controlled by a microprocessor 804 executing instructions stored in a computer readable memory 805. The instructions, when executed by microprocessor 804, cause communications device 800 to perform steps in accordance with embodiments. Computer readable memory 805 may include volatile memory, non-volatile memory, reprogrammable memory, or a combination of these. Microprocessor 804 may be any suitable kind of processor, for example a complex instruction set microprocessor, a reduced instruction set microprocessor, a digital signal processor, a microcontroller, or any other circuitry or combination of components that performs similar functions. A power subsystem 806 routes power to the other components. Optionally, a global positioning system (GPS) receiver 807 may be included, enabling communications device 800 to accurately determine its location via GPS. In some embodiments, the power subsystem may include a battery and provision for recharging the battery. An audio system 808 may include such items as a microphone and a speaker, and may provide for audio communication with the user. Other audio functions may also be provided. The depiction of communications device 800 in FIG. 8 is simplified, and other components may be present.

While the principles of the disclosure have been described above in connection with specific apparatuses and methods, it is to be clearly understood that this description is made only by way of example and not as limitation on the scope of the disclosure. 

What is claimed is:
 1. A method comprising: receiving a call at a service center from a communications device; determining, by the service center, that the call will not be connected to a customer service representative at the service center within a predetermined time; in response to the determination that the call will not be connected to a customer service representative at the service center within the predetermined time, sending a signal to the communications device indicating that the call is rejected, wherein the signal is a machine-to-machine signal directed to the communications device and not to a person using the communications device; receiving at the communications device the signal indicating that the call is rejected; and placing, by the communications device in response to the receipt of the signal indicating that the call is rejected, an outgoing call to a public safety answering point.
 2. The method as recited in claim 1, wherein sending a signal to the communications device indicating that the call is rejected comprises sending a dual tone multiple frequency (DTMF) signal across an audio link between the service center and the communications device.
 3. The method as recited in claim 1, further comprising communicating information to a user of the communications device via an automated voice response system.
 4. The method as recited in claim 3, wherein the automated voice response system informs the user of an expected wait time.
 5. A method comprising: receiving a call at a service center from a communications device; determining, by the service center, that the call will not be connected to a customer service representative at the service center within a predetermined time; in response to the determination that the call will not be connected to a customer service representative at the service center within the predetermined time, sending a signal to the communications device indicating that the call is rejected, wherein the signal is directed to the communications device and not to a user of the communications device; receiving at the communications device the signal indicating that the call is rejected; and placing, by the communications device in response to the receipt of the signal indicating that the call is rejected, an outgoing call to a public safety answering point; wherein sending a signal to the communications device indicating that the call is rejected comprises sending a short message service (SMS) message from the service center to the communications device.
 6. A method for operating a service center, the method comprising: receiving a call at the service center from a communications device; connecting the call with a customer service representative at the service center; and upon connecting the call with the customer service representative at the service center and while the call is connected with the customer service representative at the service center, sending a confirmatory message to the communications device indicating that the call has been answered by the customer service representative.
 7. The method for operating a service center as recited in claim 6, wherein sending the confirmatory message to the communications device indicating that the call has been answered by the customer service representative comprises sending a short message service (SMS) message.
 8. The method for operating a service center as recited in claim 6, further comprising placing the call in a hold status for a time after receiving the call and before connecting the call with the customer service representative.
 9. A method for operating a service center, the method comprising: receiving a call at the service center from a communications device; connecting the call with a customer service representative at the service center; communicating information to a user of the communications device via an automated voice response system, wherein the automated voice response system informs the user of an expected wait time; and upon connecting the call with the customer service representative at the service center and while the call is connected with the customer service representative at the service center, sending a confirmatory short message service (SMS) message to the communications device indicating that the call has been answered by the customer service representative. 